Skip to content

Conversation

@remypar5
Copy link

What's the problem this PR addresses?

Allowing users to specify a version or range for yarn why to find out why a specific version appears in the dependency tree. This is particularly useful if you want to address CVEs.

Closes #6859

How did you fix it?

  • Check if a version/range is specified and handling it accordingly
  • For both simple and recursive mode

Checklist

  • I have set the packages that need to be released for my changes to be effective.
  • I will check that all automated PR checks pass before the PR gets reviewed.

@remypar5
Copy link
Author

@arcanis are you available to review this? You refactored yarn why some time ago

@remypar5 remypar5 requested a review from clemyan January 6, 2026 15:39
@clemyan clemyan dismissed their stale review January 19, 2026 16:51

Requested changes have been made

Signed-off-by: Remy Parzinski <[email protected]>
@remypar5 remypar5 requested a review from clemyan February 11, 2026 11:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature] yarn why for specific package version

2 participants